NP deferred payment cooperation guide

We will explain the steps to connect NP deferred payment to Sanka and prepare for company/order data linkage.

Last updated: June 2, 2026

Guide Overview

This guide explains how to connect NP Payment to Sanka, what company and order data can be synchronized, and what to check before sending buyer or transaction data to NP Payment.

Prerequisites

Your NP Payment contract is active and you have the Merchant Code, SP Code, and Terminal ID.
You have permission to configure integrations in the Sanka workspace.
You have decided how company and order information should be maintained before sync, including company name, address, phone number, email, order amount, line items, and billing or shipping contacts.
You know whether the integration should use a staging environment or production environment.

What the integration supports

Use NP Payment when Sanka manages company and order records and NP Payment handles deferred payment registration, credit review, or transaction linkage. Depending on your workspace setup, the integration can help with:

Registering or updating Sanka companies as NP Payment buyer accounts
Importing NP Payment company information back into Sanka companies
Exporting Sanka orders or order details to NP Payment transactions
Importing NP Payment transaction information into Sanka orders
Reviewing buyer, order, billing, shipping, and credit-review status before downstream billing or fulfillment work

Connecting NP Payment does not automatically make every company or order ready for credit review or transaction sync. Confirm required company fields, billing and shipping contacts, order totals, line items, environment, and mapping before treating a failed sync as a product bug.

Sample prompt

/sanka Review this NP Payment and Sanka sync plan before making any changes. Confirm the environment, merchant information, company, buyer contact, address, phone number, email, order, amount, line items, billing and shipping details, mapping, and any action or workflow that should run. Do not export buyers, submit credit review, or sync orders until I approve the plan.

Expected behavior

After the connection succeeds, NP Payment appears on the Sanka integrations page. Company and order data sync only when the relevant import, export, action, or workflow is configured and run. For a healthy NP Payment setup:

Sanka companies include the buyer information required by NP Payment
Sanka orders include customer, amount, line item, billing, shipping, and date information before export
Imported NP Payment records preserve source details so the original buyer or transaction can be traced
Export history and action history show whether company or order sync completed, failed, or needs user correction
Downstream billing, shipping, or fulfillment steps run only when the relevant Sanka action or workflow is enabled and conditions match

NP Payment validation errors are often data-quality issues rather than code defects. Review required fields and input formats before rerunning a sync or asking AI to make a fix.

Step 1. Open the linked service screen

Open the target workspace in Sanka.
Open Integrations from Workspace.

Step 2. Add NP deferred payment

Open the create integration screen.
Select NP Payment from the list.

Step 3. Enter merchant information and save

Enter the Merchant Code, SP Code, and Terminal ID that you confirmed on the NP deferred payment management screen.
If you are connecting in a test environment, check Staging environment.
Click Update to save.

Step 4. Check the connection

Confirm that NP Payment is displayed in the integrations list.
If an error occurs, check the codes for typos and confirm whether you selected production or staging.
If the connection is healthy, proceed to company and order synchronization settings.

Step 5. Operational points

Test with a small number of companies and orders in staging before production operation.
Start with the minimum company and order fields required for sync, then add more fields as operations mature.
If the connection fails, confirm the latest merchant information in NP Payment and check whether the Sanka environment matches the NP Payment environment.
If company or order sync fails after setup, review the required fields and mapping on this page.

Sync companies and orders

To import NP Payment buyer or transaction data into Sanka, start an import from the target object, choose Integration as the source, and select NP Payment. To export Sanka data to NP Payment, select the target company or order, then choose Export and select NP Payment as the destination. Before syncing, test with a small set of records and confirm:

Company records include company name, address, phone number, email, and contact details
Order records include customer, order date, amount, line items, billing details, and shipping details
NP Payment buyer IDs or transaction IDs are saved where they can prevent duplicate registration
Import and export history shows which records succeeded, failed, or need correction

Required fields and mapping

Before exporting companies or orders to NP Payment, confirm the fields below. If your workspace uses additional fields, also check that Sanka company and order properties match the corresponding NP Payment fields.

Exporting companies to NP Payment

NP Payment field	Sanka source	Required
Buyer company name	Company name	Required
Postal code	Mapped company property	Required
Address	Address or mapped company property	Required
Phone number 1	Phone number	Required
Email address (To)	Email address	Required when invoices are sent by email
Contact name and department	Mapped company property	Optional
Invoice delivery method	Mapped company property	Optional

Phone number 1 is sent without spaces, hyphens, or parentheses, and must use a Japanese domestic phone number format that starts with 0.

Exporting orders to NP Payment

NP Payment field	Sanka source	Required
NP buyer ID	Linked company's NP buyer ID	Required for existing NP buyers
Buyer company name	Company linked to the order	Required
Postal code, address, and phone number	Linked company or mapped order fields	Required
Email address (To)	Email address on the linked company	Required when invoices are sent by email
Merchant transaction ID	Sanka order ID or mapped order property	Required
Merchant order date	Order date or mapped order property	Required
Transaction amount	Amount calculated from order line items	Required
Transaction details	Order line items	Required

If invoice issue requests are enabled, Sanka requests invoice issuance after the NP Payment transaction registration succeeds.

Importing from NP Payment

When buyer data is imported, Sanka stores the NP buyer ID, buyer company name, phone number, email address, address, review status, and billing status on the company. When transaction data is imported, Sanka stores the NP transaction ID, merchant transaction ID, order date, transaction amount, line items, transaction status, and shipping details on the order.

Troubleshooting

NP Payment is connected but company or order sync fails

Check the environment, merchant information, required company fields, order totals, line items, billing details, shipping details, and mapping. If the error is user-fixable, correct the record data and rerun only the affected records.

Buyer registration or credit review cannot be submitted

Confirm the company name, address, phone number, email, contact person, and any NP Payment-specific buyer fields. Credit review should not be submitted from incomplete or unapproved buyer data.

Orders are missing or duplicated

Review whether the order was imported from NP Payment or exported from Sanka. Then check the matching rule, source record, order number, company, amount, and whether a previous import/export already created or updated the record.

Billing or shipping information is wrong

Compare the Sanka company, contact, order billing details, shipping details, and NP Payment transaction fields. If billing and shipping contacts are different, confirm which Sanka fields are mapped before exporting again.

Downstream billing, shipping, or fulfillment did not run

Check whether the related Sanka action or workflow is enabled and whether the synced company or order matched its conditions. Treat this as a configuration issue until action history and workflow history show the downstream step should have run.

Checkpoints

Use Sanka company records, order records, import/export history, action history, workflow history, and audit logs to confirm NP Payment behavior before replying to a customer or asking AI to make a code change.

Search Sanka...

Review NP Payment integration activity

Logs

Search logsAll actionsAll dates

ID / ActionDateTarget / ItemChangeActor

3Reviewed NP Payment buyer fields2026/05/10 15:00Green Salon GroupChecked address, phone, contact, and email before buyer exportClaude integration

2Exported order to NP Payment2026/05/10 15:15Order SO-1001Confirmed amount, line items, billing, and shipping details before syncSanka integration

1Checked fulfillment workflow2026/05/10 15:30Order fulfillment workflowConfirmed downstream shipping task conditions after NP Payment syncSanka user

A safe review should include the NP Payment environment, merchant settings, Sanka company, Sanka order, required buyer and transaction fields, mapping, import/export history, and downstream billing or fulfillment workflow.

PreviousShopify Integration NextNextEngine Integration