Secure Payments By BookingSync #231

Azdaroth · 2017-05-19T18:00:01Z

No description provided.

ZenCocoon · 2017-05-20T13:24:09Z

content/guides/secure-payments-by-bookingsync.md

+
+## Preface
+
+If you have an integration with BookingSync and you create bookings on your side according to the instant booking flow (i.e. a booking gets confirmed only when the credit card payment is executed successfully) and you don't have PCI DSS compliant platform for collecting credit card payments, you can use our Secure Payments By BookingSync flow for this purpose.


Should still require at least PCI-DSS 3.1+ SAD-A when using a full client side process (JS SDK) and SAQ-D (server-to-server integration) otherwise.

Good point.

ZenCocoon · 2017-05-20T13:25:47Z

content/guides/secure-payments-by-bookingsync.md

+
+To handle integration with Secure Payments By BookingSync you need to have an application with `payments_write` or `payments_write_owned` scope. We recommend using `payments_write_owned` for this purpose to make sure the payment is not editable by anyone else, only by your application.
+
+Also, the rental for which the booking will be created requires to be instantly bookable and the it needs to have a payment gateway assigned (which will be used for executing the credit card payment) which supports the currency that is set for the rental.


typo and the it

ZenCocoon · 2017-05-20T13:28:13Z

content/guides/secure-payments-by-bookingsync.md

+
+* Create a tentative booking
+* Create a tentative instant booking payment
+* Send credit card data and payment id to our PCI DSS platform for executing payment, which will confirm both booking and payment if the payment is successfully executed


for executing payment > for executing the payment

ZenCocoon · 2017-05-20T13:29:49Z

content/guides/secure-payments-by-bookingsync.md

+
+## Creating A Tentative Booking
+
+Instant Booking flow requires payment to confirm the booking, so we recommend creating a tentative booking and leaving the confirmation to our PCI DSS platform. The confirmation process should take up to few minutes, so we recommend to set tentative expire date to 5 or 10 minutes from now. To create a tentative booking you need to provide 2 params (besides the requires one):


what about? confirmation to our PCI DSS platform > confirmation to our PCI DSS payment platform

hoo, right, looks odd without the payment

ZenCocoon · 2017-05-20T13:32:12Z

content/guides/secure-payments-by-bookingsync.md

+* tentative_expires_at - to set the expiry date
+* booked - set it to `false`
+
+You can find more about the bookings' attributes and how to create them [here](/reference/endpoints/bookings/).


Not fan of here links, what about on the [bookings endpoint documentation](/reference/endpoints/bookings/).

Fine for me

ZenCocoon · 2017-05-20T13:37:01Z

content/guides/secure-payments-by-bookingsync.md

+Another step would be creating a tentative payment (i.e. not confirmed payment) of `instant-booking` kind for the given booking. This payment will get confirmed once the successful credit card payment is executed. Here the essential attributes you need to provide for such payment:
+
+* amount_in_cents - amount in cents for the payment that will be charged
+* currency -  currency of the payment


Good to mention that it should be the same as the booking currency.

ZenCocoon · 2017-05-20T13:38:42Z

content/guides/secure-payments-by-bookingsync.md

+
+We also recommend including more details like `fullname`, `email`, `zip` and other address related field.
+
+You can find more about the payments' attributes and how to create them [here](/reference/endpoints/payments/).


same as above

ZenCocoon · 2017-05-20T13:44:04Z

content/guides/secure-payments-by-bookingsync.md

+  "card_number": 4111111111111111,
+  "cardholder_name": "John Doe",
+  "expires_at_month": "12",
+  "expires_at_year": "2020"


missing comma

ZenCocoon · 2017-05-20T13:44:38Z

content/guides/secure-payments-by-bookingsync.md

+  "address1": "some address 1 / 10",
+  "zip": "12312",
+  "city": "San Francisco",
+  "country_code": "US"


Good to provide state if using a US example.

ZenCocoon · 2017-05-20T13:49:12Z

content/guides/secure-payments-by-bookingsync.md

+
+## Executing Payment
+
+Once you have created a payment, you need to take its id and collect the credit card data.


Odd wording regarding credit card data collection. What about?

Once you have created a payment, you need to execute the payment using its id and the credit card data.

Yeah, looks sounds better.

Azdaroth · 2017-05-22T12:59:14Z

@ZenCocoon Done.

ZenCocoon · 2017-05-23T11:41:10Z

content/guides/secure-payments-by-bookingsync.md

 We also recommend including more details like `fullname`, `email`, `zip` and other address related field.

-You can find more about the payments' attributes and how to create them [here](/reference/endpoints/payments/).
+You can find more about the payments' attributes and how to create themin the  [payments endpoint documentation](/reference/endpoints/payments/).


Secure Payments By BookingSync

38daae7

Azdaroth self-assigned this May 19, 2017

Azdaroth requested a review from ZenCocoon May 19, 2017 18:00

ZenCocoon requested changes May 20, 2017

View reviewed changes

post-review adjustments, add Testing Payment Execution section

fbbac04

Azdaroth changed the title ~~[WIP] Secure Payments By BookingSync~~ Secure Payments By BookingSync May 22, 2017

ZenCocoon reviewed May 23, 2017

View reviewed changes

fix typo

ce99059

Azdaroth merged commit af490bb into master May 23, 2017

Azdaroth deleted the secure-payments-by-bookings-sync branch May 23, 2017 11:54


		## Preface

		If you have an integration with BookingSync and you create bookings on your side according to the instant booking flow (i.e. a booking gets confirmed only when the credit card payment is executed successfully) and you don't have PCI DSS compliant platform for collecting credit card payments, you can use our Secure Payments By BookingSync flow for this purpose.


		To handle integration with Secure Payments By BookingSync you need to have an application with `payments_write` or `payments_write_owned` scope. We recommend using `payments_write_owned` for this purpose to make sure the payment is not editable by anyone else, only by your application.

		Also, the rental for which the booking will be created requires to be instantly bookable and the it needs to have a payment gateway assigned (which will be used for executing the credit card payment) which supports the currency that is set for the rental.


		## Creating A Tentative Booking

		Instant Booking flow requires payment to confirm the booking, so we recommend creating a tentative booking and leaving the confirmation to our PCI DSS platform. The confirmation process should take up to few minutes, so we recommend to set tentative expire date to 5 or 10 minutes from now. To create a tentative booking you need to provide 2 params (besides the requires one):


		We also recommend including more details like `fullname`, `email`, `zip` and other address related field.

		You can find more about the payments' attributes and how to create them [here](/reference/endpoints/payments/).


		## Executing Payment

		Once you have created a payment, you need to take its id and collect the credit card data.

Secure Payments By BookingSync #231

Secure Payments By BookingSync #231

Uh oh!

Conversation

Azdaroth commented May 19, 2017

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Azdaroth commented May 22, 2017

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants